Who approves change?
The owner should know the device's purpose, required communication, update path, and acceptable outage window.
Network Inventory Builder
Turn a list of connected devices into an owned security record. Add the address, purpose, trust level, support state, administration path, and recovery note for each device, then export the inventory locally.
Inventory exists only in this page until you export it. Reloading discards the records.
Add the facts needed to operate each device
Record enough information to identify the device, decide where it belongs, update it, administer it, and recover it. Avoid secrets and passwords.
No account, database, or server submission is used.
Use the inventory to find decisions, not just devices
An inventory becomes useful when every record has an owner and a next action. Unknown support, internet-exposed administration, missing recovery, duplicate addresses, and unknown trust deserve review before cosmetic details.
Where should it communicate?
Trust level guides segmentation, but the actual access matrix should name required destinations and blocked paths.
Can it be recovered?
A reset button is not a complete recovery plan. Keep configuration backups, account recovery, replacement details, and safe disposal needs where applicable.
Reconcile the list with the real network
Compare the inventory with router client lists, wireless controller data, switch tables, DHCP leases, endpoint management, cloud consoles, and physical inspection. Each source has blind spots and old records. Investigate differences instead of assuming the longest list is correct.
Review changes on a schedule
Set a review interval that matches the network's rate of change. Home networks may use a monthly check and a review after replacing the router. Business networks should also reconcile after onboarding, offboarding, office moves, incidents, and major address or wireless changes. Record the review date with the exported file.
Use different evidence for different device classes
| Device class | Minimum operating facts | Priority warning |
|---|---|---|
| Router or firewall | Model, firmware, administrator, backup, WAN exposure, and support date | Unknown ownership or internet administration |
| Computer or phone | Owner, operating system, update state, encryption, and recovery path | Unsupported software or missing account recovery |
| Camera, printer, or IoT | Purpose, segment, required destinations, update method, and replacement plan | Broad trusted-network access or no update path |
| Server or storage | Service owner, data type, backups, listeners, dependencies, and restore test | Public exposure or untested recovery |
When a device publishes a service outside the local network, connect its owner, support state, and recovery plan to a review in the port forwarding planner.
- Investigate unknown devices before assigning a friendly name.
- Use the IPv4 address converter when an export stores addresses in unusual numeric form.
- Record the segment and required communication for every less-trusted device.
- Keep passwords, private keys, recovery codes, and personal notes outside the exported inventory.
Turn trust into boundaries
Use the network segmentation guide to build a communication matrix from the recorded trust levels. Calculate planned boundaries with the subnet calculator and document required exceptions in the firewall rule planner.
NIST consumer-router requirements in IR 8425A emphasize device identification, updates, secure configuration, and data protection. This local inventory helps organize those operational facts but does not discover devices automatically.