A remote work IT policy is the written set of rules that tells employees which devices, networks, accounts and data practices are allowed when they work outside the office. A good one fits on a few pages, names an owner, and covers eight things: eligibility, devices, home networks, access, data handling, incident reporting, backups and review. This guide walks through each, with the federal guidance behind it. It applies equally if you call it a work from home IT policy.
TL;DR
- A remote work IT policy should set technical requirements for devices, home Wi-Fi, account access and data storage, not only attendance and communication rules.
- Plan the controls on the assumption that the home or public network is hostile, and decide which devices (company-issued or personal) may touch company data.
- Regulated organizations, such as healthcare providers, must apply the same safeguards to remote staff as to office staff.
- Employees need to know exactly what to do if a laptop is lost or an account is compromised.
- Publish it, train on it, measure it and review it at least annually.
Table of Contents
- What a remote work IT policy is meant to do
- Define who may work remotely and from where
- Set device rules: company-issued, personal or both
- Specify home network requirements
- Control how employees access accounts and systems
- Set rules for data handling and storage
- Add regulatory requirements for your industry
- Tell employees what to do when something goes wrong
- Train, communicate and review the policy
- A section-by-section outline you can adapt
- Our perspective
- Put the policy into practice with Secure Techies
- FAQ
- Sources
What a remote work IT policy is meant to do
Most articles on remote work policies focus on schedules, availability and performance. An IT policy is narrower and more technical. It answers one question: how do we keep company systems and data safe when the workplace is a kitchen table, a hotel or a coffee shop?
CISA's Telework Essentials Toolkit directs organizations to develop, implement and enforce enterprise-wide policies that address the risks of an extended perimeter, including requirements for securely configuring and updating corporate devices, personal devices, mobile devices and home networks. NIST makes the same point in its telework guide: all telework and remote access components, including organization-issued and bring-your-own devices, should be secured against expected threats identified through threat modeling.
In practice, the policy has three jobs:
- Set clear rules so employees do not have to guess what is acceptable.
- Give IT a standard to build to, so device management, access controls and monitoring are consistent.
- Create a record showing auditors, insurers and clients that remote work is controlled.
It works best next to a broader plan. If you want a practical employee-facing companion, our remote work security checklist turns many of these rules into tasks people can tick off.
Define who may work remotely and from where
Start with scope. Without it, every other rule is hard to enforce.
- Eligibility: which roles or departments may work remotely, and whether the arrangement is full-time, hybrid or occasional.
- Approved locations: home offices, and whether work from public places, shared spaces or abroad is allowed. Travel outside the country is worth addressing on its own, since it changes legal and technical risk.
- Approval and revocation: who approves remote access, and under what conditions it can be withdrawn, such as a security violation.
- Who owns the policy: a named person, usually an owner, operations lead or IT manager, who answers questions and keeps the document current.
CISA advises organizations to build their policies on the assumption that approved alternate worksites contain hostile threats. That is a useful default for any small business: treat the home network as untrusted and put the protection on the device, the account and the data.
Set device rules: company-issued, personal or both
The most consequential decision in the policy is which devices may access company resources.
Company-issued devices
Company-owned laptops are the easiest to secure. The policy should require full-disk encryption, a managed endpoint security agent, automatic updates, screen lock and a prohibition on family members using the device. CISA's mobile workplace guidance recommends using organization-provided equipment for work purposes only, and the same document notes that company-furnished and personal devices may carry different security requirements to reduce risk.

Personal devices (BYOD)
If staff may use personal phones or computers, the policy needs a separate section: minimum operating system versions, required screen locks, enrollment in device management, what the company can do remotely (such as wiping company data), and what happens when the employee leaves. We cover this in detail in our BYOD policy guide.
Keep an inventory
CISA tells organizations to add devices and software introduced by teleworking to their hardware and software inventories so patching and vulnerability management are effective, and to turn on automatic updates or use a managed solution wherever feasible. A policy that requires patching is only enforceable if IT can see every device.
Specify home network requirements
You cannot manage an employee's router, but you can set a baseline and give people simple instructions. CISA's toolkit sets out the essentials:
- Use WPA2 or WPA3 wireless encryption at a minimum and disable legacy protocols such as WEP and WPA.
- Avoid a network name (SSID) that identifies your location or the router make and model.
- Change default router passwords and keep router firmware updated.
CISA's 2024 mobile workplace guidance also advises segmenting the home network, for example by putting work devices on a separate network from smart TVs and guests, and using the strongest available encryption for network activity.
Public Wi-Fi deserves its own line. NIST notes that unsecured networks used for remote access are susceptible to eavesdropping and man-in-the-middle attacks. Your policy can require a company VPN or secure remote access tool for any work done on a network the employee does not control.
Control how employees access accounts and systems
The FTC's Start with Security guide observes that a mobile workforce raises productivity but creates new security challenges, and that businesses should secure remote access points when employees, clients or service providers connect to the network.
The access section of the policy should include:
- Multi-factor authentication (MFA) on email, VPN, cloud applications and administrative accounts. Our MFA guide for business explains the options.
- Unique accounts and strong passphrases, ideally with a company-approved password manager.
- Least privilege: people get access to what their role requires, reviewed when roles change.
- Session rules: screen lock after inactivity and logging off remote connections at the end of the workday.
- Offboarding: accounts and devices are disabled or collected on the employee's last day.
On MFA rollout, CISA suggests that the CEO personally announce it and follow up with people who have not enabled it, which builds a culture of security from the top rather than leaving it as an IT request.
Set rules for data handling and storage
Most remote work incidents are data incidents: a file sent to the wrong place, a laptop left in a car, a work email forwarded to a personal inbox. The policy should say plainly where company data may live and how it may move.
CISA's telework guidance with NSA tells employees to store work content only on approved equipment and approved cloud services, not forward work email to personal accounts, and not send unencrypted sensitive content such as personally identifiable information or protected health information.
For lost or stolen devices, NIST lists the options: encrypt device storage, encrypt sensitive data on the device, or avoid storing sensitive data on client devices at all. Most small businesses combine the first and third by requiring disk encryption and keeping working files in a managed cloud workspace.
Also include practical home-office rules: lock screens when stepping away, keep work conversations and screens private from household members and visitors, and shred or securely dispose of any printed material.

Add regulatory requirements for your industry
A remote work policy does not suspend compliance duties. Staff working from home are held to the same standard as staff in the office.
Healthcare and HIPAA
HHS states that covered entities allowing employees with access to electronic protected health information to telecommute or work from home must implement appropriate safeguards, and that access controls must restrict access to people or programs that have been granted rights. The same HHS answer explains that automatic logoff is an addressable specification: you implement it if your assessment finds it reasonable and appropriate, or document that determination and use an equivalent measure.
The broader HIPAA Security Rule requires reasonable and appropriate administrative, physical and technical safeguards for ePHI, including protection against reasonably anticipated threats and ensuring workforce compliance. If remote staff use cloud tools, HHS guidance says a covered entity may use cloud services of any configuration provided it has a HIPAA-compliant business associate agreement with the provider handling ePHI.
Law firms, financial services and others
The same logic applies to client confidences, nonpublic financial information and contractual security obligations. Name the frameworks and contracts that apply to your business in the policy, and map each remote-work rule to the requirement it supports. That mapping saves hours during an audit. Our compliance and security audits are built around that kind of review.
Tell employees what to do when something goes wrong
A policy that only prevents problems is incomplete. People lose laptops and click bad links, and the damage depends on how fast IT hears about it.
The FTC tells businesses to make sure staff knows what to do if equipment or files are lost or stolen and to maintain an incident response plan covering saving data, running the business and notifying customers after a breach. Your policy should include a short reporting section:
- Report immediately to a named contact and phone number, with no penalty for honest mistakes.
- Say what happened: lost device, suspicious email, unexpected MFA prompt, shared password.
- Do not try to fix it alone: no deleting files, no wiping the machine, no paying anyone.
- IT contains first: disable accounts, lock or wipe devices and review logs.
CISA recommends that organizations review and approve a written incident response plan and invoke it even when a false alarm is suspected. The NIST small business quick-start guide adds that teams should know who has authority for each part of the plan, assess severity and root cause, contain and eradicate, and communicate confirmed incidents as laws, regulations and contracts require. HIPAA-regulated organizations must also have policies for identifying, responding to, mitigating and documenting security incidents. See our incident response plan guide and the ransomware incident response playbook for the full process.
Backups for remote teams
Ransomware is the incident most likely to cause prolonged disruption when people are scattered. CISA instructs organizations to back up systems and important files frequently, verify backups regularly, and store them offline and offsite. The policy should state that company data lives in backed-up systems, not only on a laptop's local drive. Our 3-2-1 backup guide explains how to test restores.
Train, communicate and review the policy
A policy nobody reads protects nobody. Roll it out deliberately:
- Announce it from leadership, with a short summary of what changes for employees.
- Collect signed acknowledgments at hire and after every material update.
- Train on a schedule. The FTC advises regular training, updates as new risks appear, and tracking participation. Our security awareness training overview covers how to reduce human risk.
- Measure. CISA suggests setting quarterly goals such as MFA adoption, the percentage of systems fully patched and the percentage of systems backed up. Ongoing ownership and measurable goals are also discussed in this SaaS security checklist for B2B teams.
- Practice. CISA recommends tabletop exercises with senior leaders participating, so people build the reflexes they need during a real incident.
- Review on a cycle. The Maryland Department of Commerce recommends evaluating telework policies quarterly, semiannually or annually and asking employees for input, since they may know about problems management does not.
The same Maryland document stresses that proper IT support, training and equipment are vital to a successful telework program. A rule that employees cannot follow because they lack the tools or help will be broken.
A section-by-section outline you can adapt
| Section | What it should say | Owner |
|---|---|---|
| Purpose and scope | Who and what the policy covers, including contractors | Owner or operations lead |
| Eligibility and locations | Approved roles, work locations, approval process | HR and management |
| Devices | Company-issued rules, BYOD rules, encryption, updates, inventory | IT |
| Home and public networks | WPA2 or WPA3, router hygiene, segmentation, VPN on untrusted networks | IT and employee |
| Access control | MFA, unique accounts, least privilege, session timeouts, offboarding | IT |
| Data handling | Approved storage, no personal email forwarding, encryption of sensitive data | IT and department heads |
| Compliance | HIPAA, financial, legal or contractual requirements and how remote work meets them | Compliance lead |
| Incident reporting | Who to call, what to say, what not to do | IT and leadership |
| Backups | What is backed up, how often, and restore testing | IT |
| Training and review | Training schedule, acknowledgments, review cadence | Owner and IT |
| Enforcement | Consequences for violations and exception process | HR and management |
Our perspective
Most small businesses we meet already have remote workers. What they lack is a written standard and someone watching that it is followed. A policy on paper is a start, but it only holds up when devices are managed, accounts are protected with MFA, backups are tested and a person answers the phone when an employee reports a lost laptop.
We favor proactive, preventative IT management over break-fix. For remote teams, that means monitoring endpoints around the clock, keeping patches current without relying on employees to remember, and treating the policy as a living document that is reviewed alongside real incident and ticket data. It also means tying security and compliance requirements, such as HIPAA, to the specific way each client works.
If you write the policy first and then find that you cannot enforce it, that is normal. Start with the controls that matter most: MFA, encrypted and managed devices, tested backups and a clear reporting path. Add the rest as your team and tools mature.
Alex
Put the policy into practice with Secure Techies
Secure Techies provides managed IT services and managed cybersecurity for small and mid-size businesses in Southern California, including 24/7 monitoring, a managed help desk for software and devices, endpoint detection, backup and disaster recovery, and compliance audits for frameworks such as HIPAA. If you want help turning this outline into controls your remote staff actually follow, start with our managed IT services.

For specific needs, see our cybersecurity solutions, managed help desk support and backup and disaster recovery. You can also read our broader remote work security guide and the small business cybersecurity checklist.
FAQ
How long should a remote work IT policy be?
For most small businesses, two to five pages is enough. Keep each rule short and specific, and put technical detail in a separate standard or checklist that IT maintains. Employees are more likely to follow a policy they can read in ten minutes.
Do we need a separate policy for personal devices?
If employees use personal phones or computers for work, yes, or at least a dedicated section. It should set minimum security settings, enrollment requirements and what the company can remove from the device. CISA's mobile workplace guidance notes that company-furnished and personal devices may differ in security requirements.
Does HIPAA apply to employees working from home?
Yes. HHS says covered entities that let employees with ePHI access work from home must implement appropriate safeguards, and the Security Rule's access control standards still apply. Healthcare practices should document those safeguards in the policy and confirm cloud vendors handling ePHI have a business associate agreement in place.
How often should we update the policy?
Review it at least annually, and sooner after an incident, a major tool change or a new regulatory obligation. Maryland's telework guidance suggests quarterly, semiannual or annual reviews, with employee input included.
What should employees do if their laptop is lost or stolen?
They should report it right away to the contact named in the policy, without trying to fix it themselves. IT can then lock or wipe the device, disable accounts and review access. Disk encryption reduces the risk that data on the device is exposed.
Sources
- CISA Telework Essentials Toolkit
- NIST SP 800-46 Rev. 2, Guide to Enterprise Telework, Remote Access, and BYOD Security
- CISA Federal Mobile Workplace Security, 2024 Edition
- NIST ITL Bulletin, Security for Enterprise Telework (March 2020)
- FTC Start with Security: A Guide for Business
- CISA Telework Guidance with NSA and DHS CISA
- CISA Cyber Guidance for Small Businesses
- NIST Cybersecurity Framework 2.0 Small Business Quick-Start Guide
- FTC Cybersecurity for Small Business
- HHS: Security Rule access control and telecommuting
- HHS: Summary of the HIPAA Security Rule
- HHS: Guidance on HIPAA and Cloud Computing
- Maryland Department of Commerce Telework Policy Best Practices
