A remote work security policy is a short, written set of rules that says who may work outside your office, on which devices, through which connections, with what data, and what to do when something goes wrong. For a small business the policy that works is one page per topic, tied to controls your IT team actually enforces: multi-factor authentication, encrypted and patched devices, a single approved way in, and a clear path to report problems. A policy nobody enforces is just a document. Below is what to include, in the order to write it, with the federal guidance behind each rule.
This guide is for owners and managers of Wisconsin manufacturers, law firms, dental practices, financial firms and other small organizations that have staff working from home, on the road or on a personal phone.
TL;DR
- A remote work security policy covers eligibility, approved devices, remote access methods, home office rules, data handling, training and incident reporting.
- Federal guidance from CISA and NIST tells you what to define; your job is to make each rule specific and enforceable.
- Give personal devices (BYOD) less access than company-managed ones, and keep sensitive data off them.
- Treat the policy as a living document: review it when your tools, staff or compliance duties change.
- Rules on paper only work when monitoring, patching and authentication enforce them every day.
Table of Contents
- What a remote work security policy is, and how it differs from related policies
- Start with scope: who, where and what
- Remote access rules: one approved way in
- Company devices and BYOD
- Home office checklist
- What employees do: daily habits and reporting
- Industry notes for Wisconsin firms
- Writing it, rolling it out, keeping it alive
- Turning the policy into daily practice
- Our perspective
- FAQ
- Sources
What a remote work security policy is, and how it differs from related policies
People use several names for overlapping documents, so it helps to separate them.
- Remote work (or telework) security policy: the umbrella. It covers people, places, devices, data and behavior when work happens away from your office.
- Remote access policy: the technical part. It names the permitted ways to connect to your systems (VPN, a virtual desktop, a cloud application), who gets which level of access and how accounts are created and removed.
- BYOD policy: the rules for personal phones, tablets and laptops used for work. "BYOD" means bring your own device.
- Network security policy: how your own office network and servers are protected. It sits alongside the remote policy but is not the same thing.
For a business with 10 to 200 people, one document with a clear remote access section and a BYOD section is easier to maintain than four separate ones. NIST's guide on telework and remote access says a telework security policy should specify the permitted remote access methods, the device types allowed for each, each user's access level, account provisioning, remote access server administration and how the policy is updated. That list makes a good skeleton.
You do not need a security department to do this. The FCC's cybersecurity planning guide was built for businesses without dedicated security staff and says that even a business with a single computer or credit card terminal can benefit from its planning approach.
Start with scope: who, where and what
The first section answers three questions before any technology comes up.
Who may work remotely. CISA's guidance for policy writers lists the basics: who may telework, which services are available to them, restrictions on information, maintenance guidelines, VPN information, training and user guidelines. In a small firm, translate that into roles. A shop-floor supervisor who checks production reports from home needs different access than a bookkeeper handling payroll files or a paralegal opening client matters.
Where work may happen. Name approved locations: home office, client sites, travel. State plainly that public Wi-Fi is not approved for company business unless the connection is encrypted. Same guide recommends organizations assume approved alternate worksites may contain hostile threats, a useful mindset: your policy should not depend on the home network being safe.
What data may leave the building. Classify in two or three plain tiers. For example: public marketing material, internal business files, and regulated or confidential data (client files, patient records, customer financial information, engineering drawings). Then say which tiers may be opened remotely, and which may never be stored on a personal device.
If you are comparing tools to support a scattered team, remote workforce software options can help you think through which services staff will use, and each approved service belongs in the policy's list of permitted tools.
Remote access rules: one approved way in
This is the section that does the most to reduce risk. Define the approved methods and ban everything else.
- Require multi-factor authentication (MFA) everywhere remote. CISA's mobile workplace guidance calls for MFA and authorized remote access mechanisms, and the FCC's small business guide recommends a secure VPN with strong two-factor authentication when you give staff internet access to your internal network. Our own explanation of why MFA matters for your business covers the practical rollout.
- Use encrypted connections only. The Oklahoma state checklist for remote workers recommends encrypted protocols such as VPN, IPsec or SSL, and says that where VPN is the organization's practice, it should be the only route to sensitive information.
- Give least-privilege access. New Jersey's cybersecurity cell advises limiting remote users to the web applications, SaaS or virtualized applications they need rather than the whole internal network, and scoping VPN access the same way. A salesperson does not need a route to the file server that holds your accounting data.
- Never expose remote desktop directly to the internet. Open remote desktop ports are a common ransomware entry point. Our guide to remote desktop security explains the controls that close that door.
- Define how accounts start and stop. Say who approves new remote access and how quickly it is removed when someone leaves. This is where small firms most often have gaps.
CISA's June 2024 joint guide, Modern Approaches to Network Access Security, describes the move away from broad, traditional remote access deployments toward finer-grained access controls. For a small business, the practical takeaway is to tie access to the identity of the user and the health of the device, not to a network address. We cover that thinking in identity-first security for SMBs.
Company devices and BYOD
Company-managed devices
The policy should say that work happens on company-managed devices wherever possible, and that those devices are kept up to date. NJCCIC's recommendations for remote devices include endpoint hardening, anti-malware, endpoint detection and response, web filtering, host firewalls, device and file encryption, current patches, monitoring and incident reporting. Write these as requirements: full-disk encryption on, automatic patching on, protection software installed and not removable by the user.
Two of those deserve their own attention. Unpatched laptops are an easy target, so see our patch management best practices. And antivirus alone no longer catches everything, which is why endpoint detection and response belongs on every laptop that leaves your building. DNS filtering also blocks known bad sites wherever the laptop is; see DNS filtering for business.
Personal devices (BYOD)
If staff use personal phones or laptops, set tiered rules. NIST recommends risk-based, tiered access: organization-controlled computers may get broader access, BYOD computers limited access, and BYOD phones or tablets only low-risk resources such as webmail. A workable small business BYOD section requires:
- Written approval before a personal device connects, and a list of supported device types.
- Current operating system patches and device encryption.
- A screen lock, strong authentication and MFA.
- Anti-malware and basic security controls.
- Access to only the applications and data the person needs.
- No downloading of sensitive data to the device or to personal cloud storage.
That last rule matches CISA's Telework Essentials Toolkit, which advises avoiding storage or transmission of sensitive organizational information on personal devices. NIST also suggests conditional access controls, which check the device before allowing a login, and considering separate network segments where BYOD connects to enterprise facilities.
For a manufacturer, add a line about the plant floor: personal devices never connect to production or operational technology networks. For a law firm or dental practice, add that client or patient files are opened only through the approved application, never saved locally or sent to personal email.
Home office checklist
Home offices lack many of the physical safeguards of an office. CISA's 2024 guide recommends a separate workspace, protection of data and equipment, and keeping family and friends from using work equipment. It also suggests an employee self-certification of the workspace. Here is a checklist you can hand to each remote employee to sign.
Devices and data
- Work only on the company-issued or approved device.
- Lock the screen whenever you step away.
- No family or friends use the work device, even briefly.
- Store files only in approved locations; dispose of printed material safely.
- Report a lost or stolen device immediately.
Home network
- Change the default router password and use a strong one.
- Use WPA2 or WPA3 wireless security; turn off the older WEP and WPA standards.
- Pick a network name that does not reveal your address or router model.
- Disable remote management of the router.
The router items come straight from CISA's Telework Essentials Toolkit, which also suggests protective DNS. Oklahoma's checklist adds that router remote management should be disabled when the management access cannot be encrypted. Our post on business Wi-Fi security controls covers the same ground for the office side.
Physical space
- A separate work area where possible, positioned so screens cannot be seen from windows or by visitors.
- Doors and windows that lock, and adequate lighting.
- Devices put away or locked when not in use.
Travel and public places
- Avoid public Wi-Fi for company business. The Oklahoma checklist allows it only with an encrypted protocol and MFA.
- Use a privacy screen in shared spaces and never leave a laptop in a vehicle.
What employees do: daily habits and reporting
CISA's toolkit makes a point worth repeating in your policy: secure remote work depends on recurring habits, namely patching, authentication, phishing awareness and safe handling of removable media, and not on a VPN alone. Put those habits in the user responsibilities section:
- Use MFA and only the approved access method.
- Install updates when prompted, and never disable security software.
- Be suspicious of unexpected email, texts and calls, especially requests involving money or credentials.
- Do not plug in unknown USB drives.
- Report suspected phishing, loss or breach as soon as possible.
The last point is where many policies fall short. CISA's guidance says suspected phishing goes to the designated security office and that loss or breach is reported as soon as possible. In your policy, replace "designated security office" with a real name and phone number, and state there is no penalty for reporting a mistake quickly. A fast report of a clicked link costs far less than a hidden one.
Training makes the rules stick. The same CISA guide names phishing, social engineering, information security and operational security among the topics for remote workers. Start with our practical phishing training guide for small businesses, and run short refreshers at least yearly and whenever a new threat appears.
Industry notes for Wisconsin firms
The core policy is the same everywhere, but the emphasis shifts.
- Manufacturers: protect design files and customer specifications, keep remote access away from production systems, and plan for downtime. A remote session that reaches the plant network can stop a line. Our guide to OT patch management for manufacturers covers the shop-floor side.
- Law firms: client confidentiality is the priority. Limit access by matter, require MFA, and prohibit local storage of client files on personal devices.
- Dental and medical practices: patient records must stay inside approved systems. Lock down remote access to practice software and require device encryption on anything that touches it.
- Financial firms: auditors and regulators ask for documented controls. Keep the policy, training records, access reviews and incident reports where you can produce them quickly.
Whichever applies to you, confirm the specific legal duties with your attorney or compliance adviser, and write the resulting requirements into the policy.
Writing it, rolling it out, keeping it alive
A practical sequence for a small business:
- Inventory. List who works remotely, on what devices, reaching which systems.
- Draft the sections above in plain language, one or two pages each at most.
- Match every rule to a control. If the policy says "all laptops are encrypted," someone must be able to show a report proving it. Rules you cannot check should be rewritten or dropped.
- Collect signatures on the acknowledgment and the home office self-check.
- Train at onboarding and on a schedule.
- Review at least yearly, and after any incident, new tool or change in staffing. NIST's guidance includes policy updates as an element of the policy itself.
Step three is where most small firms stall. Writing "devices must be patched" is easy. Knowing, today, that every laptop is patched, encrypted and monitored is the hard part, and it is why the policy and the day-to-day IT work belong together. If you want a quick view of where you stand before drafting, the Free IT Risk Score gives a 60-second read on your exposure.
Turning the policy into daily practice
We built our managed services so that the controls in a remote work policy are already running. Managed IT Services from Collett Systems come with a fixed cost per user and a standardized, fully loaded stack that includes 24/7 monitoring, proactive support, security management, backup and disaster recovery, compliance documentation and an unlimited help desk. Strategic IT planning and audit readiness are included, not sold as add-ons. Over 150 local organizations in West Bend and Southeastern Wisconsin work with us.
If you want to know which gaps your current remote setup has before you write rules around it, start with the IT & Security Assessment.
For very small teams and solo operators, Total Secure offers managed security. If you already have internal IT staff, Co-Managed IT Services fits alongside them.
Our perspective
A policy is a promise you make to your clients, your insurer and your employees. It only counts if it is true on a Tuesday afternoon, when someone is working from a kitchen table.
We see remote security as infrastructure, not an expense. That is why we price it per user, and why monitoring, patching, authentication and documentation come as one standard stack. When the rules, the tools and the records all come from the same team, nothing falls between them, and the policy you hand an auditor matches what is running.
Write the rules short. Enforce them with tools. Review them every year. No smoke and mirrors.
Dustin Collett
FAQ
Do we need a remote work policy if only a few people work from home?
Yes. The risk comes from the device and the access, not the headcount. One unpatched laptop with access to your file server is enough. A short policy covering approved devices, MFA and reporting is a good start, and it can grow as your team does.
What is the difference between a remote access policy and a remote work security policy?
The remote access policy is the technical section: approved connection methods, device types per method, user access levels and account management. The remote work security policy is broader and also covers home office rules, data handling, training and incident reporting. Most small businesses keep both in one document.
Should we allow employees to use personal devices?
It can work with limits. Require approval, encryption, current patches and MFA. Give personal devices narrower access than company devices, and keep sensitive data from being downloaded or saved to personal storage. NIST's guidance suggests only low-risk resources, such as webmail, for personal phones and tablets.
How often should the policy be updated?
Review it at least once a year, and again after an incident, a new application or a change in who works remotely. Re-sign acknowledgments when significant changes are made, and repeat training so staff know what changed.
Sources
- CISA, Federal Mobile Workplace Security, 2024 Edition
- CISA, Telework Essentials Toolkit
- NIST SP 800-46 Rev. 2, Guide to Enterprise Telework, Remote Access, and BYOD
- FCC Cyber Security Planning Guide
- Oklahoma OMES, Checklist for Securing Remote Workers
- NJCCIC, Tips for Teleworkers: Remote Access Security
- CISA, Modern Approaches to Network Access Security
- Remote workforce software options
