Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Protect information when people work remotely – at home, while travelling or in co-working spaces.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Teams should define secure remote-working expectations that match the kinds of locations people actually use. The main weakness is assuming the office model still applies when staff work from home, hotels, client sites, or shared spaces, where devices, screens, networks, and conversations face different exposure. Teams should turn broad rules into practical checks, accountable roles, and recorded exceptions.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Remote access is allowed from unmanaged devices or weakly protected endpoints, increasing exposure through local storage, browser sessions, and saved credentials.
People use public networks and shared spaces without screen privacy or clean-desk discipline, allowing inadvertent disclosure to bystanders or family members.
Remote-working exceptions are agreed informally, so device, printing, and travel rules are applied unevenly and cannot be traced back to an owner.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
State which work locations are permitted, which are prohibited, and which need extra safeguards. Define minimum technical conditions: managed laptop, full-disk encryption, strong authentication, screen lock, endpoint protection, and approved remote access such as VPN or zero-trust access. The IT or security owner should validate the baseline and handle exceptions.
Describe practical behaviors for home, travel, and co-working use: avoid displaying sensitive information near others, prevent unattended screens, restrict local printing, and use privacy filters where appropriate. Make line managers accountable for reinforcing these rules during onboarding, annual refresh, and after incidents involving exposure in public areas.
Add a short exception process for non-standard situations such as international travel, temporary equipment shortages, or client-site work. Require the risk owner to approve compensating controls, such as time-limited access, additional logging, or removal of offline storage. Record the reason, duration, and closure date so the exception does not become permanent by accident.
Keep supporting evidence in a practical file set: issued device list, remote-access configuration, acknowledgement of teleworking rules, and training completion. Review logins from unusual geographies, repeated policy breaches, or repeated printing exceptions to identify whether the guidance needs tightening or additional awareness. Feed recurring failures into corrective action.
What an auditor will ask to see
Signed acknowledgement of remote-working rules tied to the employee or contractor record.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.