Municipal USB Drives: A Safer Process for Incoming Files

Give the counter a clear starting point

Imagine a village resident bringing photographs of a damaged park bench to the office on a USB drive. The employee wants to get the pictures to public works, and the nearest available computer handles payments and resident inquiries. Helping the resident should not require that employee to make a new security decision while someone waits at the counter.

Michigan township, village, and city offices need a straightforward process for receiving outside files. The National Cyber Security Centre identifies removable media as a possible route for malicious software and a source of data-loss risk. Start by deciding how residents and vendors should provide routine documents, which staff can accept them, and where an unusual request goes for help. Put those instructions where the people covering the counter can find them.

Make the approved submission route usable

Agree with the department owner and IT on the normal delivery method. It might be an existing municipal form, an approved upload service, or another established channel. Give staff the exact address or instructions, accepted file types, size limits, and the contact for someone who needs assistance. Keep this guidance consistent with the municipality's existing submission procedures.

In the park example, the employee could explain how to send the photographs through the approved route and identify the department that receives them. Have a practical alternative for a resident who cannot use that route. Changing the delivery method does not remove the need to check incoming files: NCSC guidance explains that malicious content can arrive through network transfers as well as removable media. Ask IT how protection and review apply to the chosen channel.

Keep unfamiliar drives out of routine work computers

Give employees a simple rule for an unfamiliar or found drive: do not connect it to a work computer to see what is on it. Use the approved handoff to IT. A handwritten label or a familiar sender does not establish how a device has been used or what it contains. Staff should be able to explain the office's process without suggesting that the resident did anything wrong.

Include devices left behind after meetings, vendor-supplied drives, and requests to borrow an employee's personal laptop for the transfer. An alternative computer still needs an approved handling method. If the municipality takes custody of a device, record the source, purpose, receiving employee, and next owner without opening it. Keep it in the agreed location until the responsible person provides instructions.

Have IT demonstrate the device controls

Ask your provider what the current computers permit and whether those settings match the office procedure. Microsoft's Defender for Endpoint documentation, for example, describes controls for allowing or restricting removable devices and for controlling read, write, and execute operations. The available approach depends on the systems, management tools, and configuration in use. Have IT explain what is actually deployed rather than assuming a general security product name answers the question.

Review necessary uses before making changes. An approved municipal storage device may support a specific export or a vendor's agreed workflow. Identify the affected employees, devices, and tasks, then arrange a controlled test. Check both the restriction and the approved work that must continue. A staff member encountering a blocked device should know the support contact and how to request a reviewed exception.

Make necessary exceptions specific

Some outside files may still require a physical transfer. Give that situation a defined path involving the department owner and IT. Specify why the transfer is needed, which files are expected, who authorizes the work, and where the approved result belongs. Have IT decide the technical handling and checks before anyone connects the media. An old spare computer does not become an approved intake station just because it is available.

Give the employee receiving the checked files enough information to finish the handoff. Confirm that the intended documents arrived, are usable through approved applications, and reached the correct staff owner. Assign any missing or unexpected items for follow-up. Agree on how the physical device is returned or retained and how temporary working copies are handled under the municipality's established procedures. Keep the exception tied to its stated purpose.

Make an accidental connection easy to report

If someone has already connected an unfamiliar drive or sees an unexpected prompt, give them a known support route and encourage an immediate report. Stop interacting with the files and follow IT's instructions. Provide the computer identifier, approximate time, device source if known, and what appeared on screen. Avoid trying the drive in additional computers to compare results.

Keep the reporting conversation factual. The useful outcome is that support can assess the event and direct the next steps while the department arranges an approved way to continue the resident's request. Include this scenario when training anyone who covers the counter, including temporary staff.

Review one file-intake workflow with this checklist

Choose one department that regularly receives outside files and walk through its process with a covering employee and IT. Use approved sample material for the rehearsal.

• Staff can find the current submission instructions and assistance contact.
• The resident has a usable approved way to provide the required files.
• Unfamiliar media has a clear handoff that avoids routine work computers.
• IT has demonstrated the relevant restrictions and necessary approved uses.
• Exceptions identify the approver, handler, expected files, and destination.
• Staff know how to report an accidental connection and finish the request.