Project & Development
VPN, Remote Access, Device Inventory: List NAS, Printers, Cameras, Then Secure Them
Intermediate | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)
Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.
Inventory template for the VPN, remote desktop, and vendor maintenance links into your office network, plus NAS, printers, cameras, and Wi-Fi gear. In Japan, the National Police Agency's 2025 figures show over 80 percent of infection routes reported by ransomware victims were VPN equipment and remote desktop; check its latest release. Find entry points from device ledgers, admin screens, contracts, and vendor inquiries, never by probing from outside. Small firms often miss vendor-built maintenance links nobody inside knows, updates left to the seller, default admin passwords, and links left open after work. Start from the accounting payment list to spot maintenance and lease vendors. Change default or possibly leaked passwords, not on a schedule, and prefer an authenticator app or passkey over SMS. Four A4 whiteboard pages cover listing, checking, deciding what to close, and keeping updates running. The task board has 4 parent tasks and 12 subtasks in five columns.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
VPN, Remote Access, Device Inventory
How to use (4 pages): ① Write the purpose, list entry points and devices, tabulate vendors (frames①–③) → ② Check updates and sign-in, review pitfalls (frames④–⑦) → ③ Sort by importance × urgency, decide to close, update, or keep (frames⑧⑨) → ④ Set update checks and notice flow, agree with vendors (frames⑩–⑫)
1/4 List entry points, devices
① Inventory purpose and scope (start here)
- Purpose e.g. Know every entry from outside to the company network and close the ones nobody uses
- Scope e.g. Devices on the network at HQ and the warehouse. Employees' personal phones are out this time
- Period and owner e.g. Two weeks. One person from general affairs and one employee who knows devices
② Entry points from outside and devices on the company network
- Company network
- VPN equipment e.g. One VPN device at HQ, used daily for remote work
- Remote desktop e.g. A setting to reach the accounting PC from outside. Who uses it is unknown
- Maintenance link e.g. A port the printer vendor uses to inspect remotely
- NAS e.g. One unit for shared folders. Unknown whether it opens from outside
- Printers e.g. Two units. Scans are set to go out by email
- Cameras and Wi-Fi e.g. Four cameras viewed on phones. Two Wi-Fi routers
③ Installer and internal admin for each device in ②
| Installed by | Admin inside | Document checked | |
|---|---|---|---|
| VPN and remote | e.g. Company A, which laid the line. Maintenance link is also Company A | e.g. General affairs. But they have not looked at the settings | e.g. Company A's quote and maintenance contract |
| NAS and printers | e.g. NAS bought by us. Printers leased from Company B | e.g. No one for the NAS, so general affairs takes it | e.g. Lease contract and the delivery slip from purchase |
| Cameras and Wi-Fi | e.g. Cameras by Company C. Wi-Fi set up by us | e.g. Store manager for cameras. No one for Wi-Fi | e.g. Company C's invoice and the label on the device |
2/4 Check updates and sign-in
④ Update and sign-in strength of the six devices from ②③
| Update status | Sign-in strength | Where checked | |
|---|---|---|---|
| VPN equipment | e.g. Last updated a year ago. Asking Company A if it is the latest | e.g. ID and password only. No multi-factor authentication | e.g. Version on the admin screen and an inquiry to Company A |
| Remote desktop | e.g. The PC updates itself to the latest | e.g. Password only. Unclear whose ID it is | e.g. The PC's settings screen |
| Maintenance link | e.g. Left to the vendor and unknown | e.g. No one inside knows the vendor's ID | e.g. Asked Company A for its work records |
| NAS | e.g. Stopped two years ago | e.g. Admin ID and password still at the default | e.g. The NAS admin screen |
| Printers | e.g. Company B updates once a year | e.g. Admin password still at the default | e.g. Company B's inspection report |
| Cameras and Wi-Fi | e.g. Unknown for cameras. Wi-Fi updates itself | e.g. The camera app asks for an authenticator app check | e.g. Inquiry to Company C and the router's admin screen |
⑤ Pitfall: a link the vendor built
- What happens: e.g. A link built for past maintenance stays open and nobody inside knows it
- How to check: e.g. Read the maintenance contract and work reports, and ask the vendor "Please list every connection you built for us"
- The fix: e.g. Add the links you hear about to the table in ③ and have the vendor shut off unused ones
⑥ Pitfall: updates left to the seller
- What happens: e.g. The contract has no updates in it, and the device has run an old version for years
- How to check: e.g. Look for an updates clause in the contract, and if none, ask the vendor who updates and when
- The fix: e.g. Decide the update owner in the table in ⑩, and write what the vendor handles in the agreement in ⑫
⑦ Pitfall: password left at default
- What happens: e.g. The admin screen is used with the default password printed in the manual
- How to check: e.g. Ask the admin if there is a record of changing it. With no record, treat it as unchanged
- The fix: e.g. Change it to a long password used only on that device, and add multi-factor authentication if offered
3/4 Decide what to close first
⑧ Sort the entries found in ④–⑦ by importance × urgency
Vertical axis: High importance / Horizontal axis: High urgency
- Plan it Reachable from outside, but updates are still running. Schedule it within the month e.g. Add multi-factor authentication to the VPN equipment
- Do now Reachable from outside and hit by a default password, stopped updates, or nobody knowing about it. Start this week e.g. Have Company A shut off the maintenance link it built
- Skip Not connected to the outside and a small problem. Just keep it in the ledger in ③ this time e.g. Tidy the names of an old printer used only inside
- Delegate Urgent, but not an entry from outside and low impact. Hand it to the vendor or an internal owner and set a deadline e.g. Ask Company B to update the printers used only inside
⑨ Decide for the do now and plan it entries from ⑧ (close, update, keep)
| Decision | Reason | Deadline and owner | |
|---|---|---|---|
| Entry 1 | e.g. Company A's maintenance link, close | e.g. The current contract does not use it | e.g. This Friday, ask Company A |
| Entry 2 | e.g. VPN equipment, update | e.g. Used daily for remote work. The version is old | e.g. Week 2, general affairs and Company A |
| Entry 3 | e.g. Remote desktop to the accounting PC, close | e.g. The same work can be done over the VPN | e.g. This Wednesday, the employee who knows devices |
| Entry 4 | e.g. Phone viewing of cameras, keep | e.g. The manager uses it daily. It asks for an authenticator app check | e.g. Review the keep condition in the table in ⑩ every 3 months, the manager |
4/4 Keep updates on a cycle
⑩ How to run updates for the devices you decided to update or keep in ⑨
| How to check | How often | Owner | Where to record | |
|---|---|---|---|---|
| VPN equipment | e.g. Compare the admin screen version with the maker's notice | e.g. Once a month | e.g. General affairs | e.g. Date and version in the update status of ④ |
| NAS | e.g. Look at the update screen in the admin screen | e.g. Once a month | e.g. The employee who knows devices | e.g. Date and version in the update status of ④ |
| Printers | e.g. Confirm the version from Company B's inspection report | e.g. At each inspection | e.g. Company B. General affairs confirms | e.g. Save the inspection report in the shared folder |
| Cameras and Wi-Fi | e.g. Ask Company C about updates and look at the router screen | e.g. Once every 3 months | e.g. The store manager | e.g. Date and version in the update status of ④ |
⑪ From an update notice to the record
- Receive The owner compares the maker's notice or vendor message with the devices in the ledger in ③ e.g. Do not click the email link, reopen the maker's bookmarked site
- Confirm Check in the maker's notice whether the device and version are affected, and whether it is urgent e.g. If it is urgent, put it in do now in ⑧
- Update Update during quiet hours and check the version on the admin screen afterward. For devices the vendor handles, set a date and ask them e.g. Update the NAS after work on Friday
- Record Write the date and version in the record column of the table in ⑩ e.g. Write the VPN equipment's new version and update date in the ledger
⑫ Agreement with vendors (pitfall: connections not closed after use)
- What happens e.g. A vendor's connection stays open after maintenance ends
- How to check e.g. Check every time that the work report states when the connection was closed
- The fix (agreement with vendors) e.g. Open the maintenance link only on the day of the work, close it when the work is done, and report. Contact us within 3 business days of an update notice
Task board contents
Unchecked 16 items
Map entry points
On page 1, write the purpose and scope, list the entry points from outside and the devices on the company network, and tabulate the vendor who installed each and the admin inside. Once the list exists, the later pages just check it item by item. Press Ctrl+F (⌘F on Mac) and type "3/4" to jump to page 3.
Pull vendor names
First step. Open the accounting payment list (past 12 months), pick out maintenance, lease, and internet line vendors and what devices each handles, and write them in the Installed by column of frame ③. Done once the vendor names are listed, in about 15 minutes. Also write one line for the purpose in frame ①.
Fill the branches
In the six branches of frame ②, write where each device sits and how many there are. Check device labels, admin screens, and maintenance contracts, and ask the vendor about anything unclear. Done when all six branches have a line.
Vendors and admins
In the table of frame ③, match the vendor names from the first subtask to devices, then add the admin inside and the document you checked. Assign an owner on the spot for any device without one.
Check their status
On page 2, tabulate update status and sign-in strength for the six devices from page 1 and review three pitfalls. The old versions, weak sign-in, and unknown links found here decide the closing order on page 3.
Check six updates
In the update status column of frame ④, write the last update and whether it is the latest version. Check the version on the admin screen or with the vendor. Done when all six rows are filled.
Rate login strength
In the sign-in strength column of frame ④, write whether it is password only or has multi-factor authentication. An authenticator app or passkey is strong, while SMS is better than nothing but weaker.
Review 3 pitfalls
For each pitfall in frames ⑤–⑦, check whether it happens at your company and rewrite what happens, how to check, and the fix. Mark any that apply in the table of frame ④.
Set closing order
On page 3, sort the entries found on page 2 by importance × urgency and decide with reasons whether to close, update, or keep each. This parent task is about not fixing everything at once but starting with weak entries reachable from outside.
Sort into 4 groups
In frame ⑧, sort the entries found in frames ④–⑦ onto sticky notes in four groups, do now, plan it, delegate, and skip. Done when every entry is in one group.
Decide and explain
In the table of frame ⑨, list the entries in do now and plan it, then write the decision (close, update, or keep), the reason, the deadline, and the owner. For entries you keep, also write the condition for keeping.
Ask for urgent work
Ask the vendor or the internal owner to handle the entries you decided to close in frame ⑨, and add the request date to the Deadline and owner column of frame ⑨. Move items sent to a vendor to the Vendor working column of the task board.
Run the updates
On page 4, decide how, how often, and by whom each device you keep is checked for updates, and write the flow after an update notice and your agreement with vendors. Make this a continuing review, not a one-off. Track the devices in the Review regularly column of the task board.
Set check frequency
In the table of frame ⑩, write how to check, how often, who, and where to record, for each device. Done when all four rows have an owner's name.
Set the notice flow
In the four steps of frame ⑪, write your own way from receiving an update notice to recording it. Make it a rule not to click links in notice emails but to reopen the maker's site from a bookmark.
Agree with vendors
Check that the latest work report states when the connection was closed. Then in frame ⑫ write that maintenance links are opened only on the day of the work and closed afterward, and that the vendor contacts you on update notices. Tell the vendor and get a reply. Done when the reply is written in frame ⑫.