An employee works at home, at the kitchen table, on a customer contract with the screen in plain view; the draft that came out of the printer goes into the household bin in the evening. Remote and hybrid working is the most common scenario in which information leaves the organization’s physical and network boundaries. It can’t be managed with general usage rules: who can see the screen at home, where printed documents are disposed of, which data can be accessed from a personal device all go unanswered. Below we explain, with sample clauses, the scope, authorization criteria, device scenarios and employee obligations of a remote working security policy that meets ISO/IEC 27001:2022 Annex A 6.7.
Purpose of the control and policy scope
Annex A 6.7 requires security measures to be implemented when personnel work remotely, to protect information accessed, processed or stored outside the organization’s premises. The control doesn’t work on its own. The remote working policy is usually read together with these controls:
- 8.1 User endpoint devices: Device configuration and protection.
- 7.9 Security of assets off-premises: Carrying laptops, phones and documents.
- 7.7 Clear desk and clear screen: Applies at home and in shared spaces too.
- 6.8 Information security event reporting: The remote employee’s reporting route.
In the scope section, state clearly which working arrangements fall under the policy: regular home working, hybrid working, working while travelling, coworking spaces and out-of-hours emergency interventions. Remote access by supplier personnel is a different risk profile. Manage it with a separate supplier access procedure.
What the policy won’t say is also part of its scope. The VPN protocol, encryption algorithm or endpoint management profile go into technical standards, not the policy. The policy says “the secure connection method approved by the organization is used”; the technical standard sets which method is approved. The technology changes, the policy stays put. It doesn’t go back for re-approval.
Remote working authorization
Not every role can work remotely in the same way. The authorization section defines under which conditions and with whose approval remote working is granted. Working arrangements are set by employment law and HR policy; the information security policy adds conditions based on the information to be accessed.
Authorization criteria:
- Class of information to be accessed: Additional restrictions (company device only, no printouts) are defined for roles working with “Confidential” information.
- Customer and contract terms: For information such as prototype data or engineering data belonging to a customer, the customer contract may restrict remote access.
- The role’s system access: Privileged administrator access is granted remotely only through strengthened methods.
- Geography: Working from abroad is assessed separately in terms of cross-border transfer of personal data and customer terms.
The approval record is kept together with a declaration showing the employee read and accepted the policy. The way authorization is reflected in access rights must be consistent with the principles in the access control policy writing guide.
Authorization isn’t granted once and forgotten. A role change, assignment to a project with “Confidential” information or a request to work from abroad triggers reassessment. At least once a year, compare the list of staff authorized to work remotely with users who have active accounts on the remote access system. In practice this means putting the member list of the AD group that grants VPN access next to HR’s approval list. A user who isn’t on the list but connects shows authorization was bypassed. The dated output of the comparison is the most direct evidence that the control is operated.
Company device and personal device scenarios
The most debated section of the policy is personal device use. It’s hard to prove information is protected on a device the organization can’t manage. That’s why, if personal devices will be allowed, the scope of access is narrowed.
| Topic | Company device | Personal devices |
|---|---|---|
| Management | Full device management | App-level protection or browser access |
| Disk encryption | Mandatory, verified centrally | If it can’t be verified, local data storage is prohibited |
| Information that can be accessed | All of the role’s permissions | Email, collaboration tools; no “Confidential” data |
| Loss/theft | Remote wipe | Wipe of corporate data only |
| Confidentiality | The organization may monitor; employees are informed | The personal area isn’t monitored |
Don’t skip the privacy row for personal devices. The policy must clearly state that the organization won’t access photos, location or personal apps on the personal device, and will wipe only corporate data in case of loss. The scope of employee monitoring is communicated in line with the information obligation under KVKK. If this isn’t written down, the employee won’t enroll their device and will forward email to a personal app; the control stays on paper.
On company devices, policy obligations must be technically verifiable. On a Windows laptop, the status of disk encryption can be seen with these commands (with administrator rights):
Get-BitLockerVolume -MountPoint "C:" |
Select-Object MountPoint,VolumeStatus,ProtectionStatus,EncryptionMethod
manage-bde -status C:
The point to watch: if VolumeStatus is “FullyEncrypted” but ProtectionStatus shows “Off”, encryption is suspended; it’s usually a protector not re-enabled after a BIOS or operating system update. Instead of checking devices one by one, use the endpoint management tool’s compliance report; that report is also audit evidence.
Physical security at home and printed documents
The part most often skipped in remote working policies is the physical environment. Sample clauses for someone working at home or in a shared space:
5.1 The employee works in a position where unauthorized people can’t see the screen; in public places, they use a screen privacy filter.
5.2 The screen is locked when leaving the device; the device isn’t left visible in a vehicle.
5.3 Meetings with confidential content aren’t held where the conversation can be overheard by others.
5.4 “Confidential” information isn’t printed at home. Other printed documents are kept in a locked area and aren’t thrown away at home; they’re brought back to the office and handed into the disposal process, or destroyed with a shredder approved by the organization.
5.5 Organization-owned devices aren’t made available for use by others, including family members.
Clauses should be short, observable and about behavior within the employee’s control. The sentence “The employee makes the home environment secure” doesn’t say what’s expected; it’s neither applied nor audited. For writing readable clauses, the approach in the acceptable use policy guide can also be applied to remote working clauses.
Connection and data storage rules
Connection rules are written in the policy as principles, with technical detail left to the standard:
- Corporate systems are connected to only through the remote access method approved by the organization and with multi-factor authentication.
- For the home network, changing the router administrator password from its default and using current wireless encryption are expected; the organization provides a short guide on this.
- On public wireless networks, work is done only through the approved remote access method.
- Work data is kept only in storage areas approved by the organization; it isn’t moved to personal cloud accounts, personal email or unapproved USB sticks.
- Remote administrator access is done with the additional controls defined in the privileged account procedure.
The home network isn’t under the organization’s control. A smart TV, game console and a guest’s phone sit on the same network. That’s why the policy is based not on trusting the home network but on protecting the connection itself. Whether the approved remote access method is VPN or zero trust access is a technical decision; the options are covered in the ZTNA vs VPN comparison. What matters for the policy is that the chosen method is written in the technical standard and that the policy clause refers to that standard.
Remote working can also be part of the business continuity strategy. Test the assumption that all staff can work remotely when the office is inaccessible in terms of capacity, licenses and devices; the concurrent VPN session limit is often the first bottleneck. This aspect is discussed in the article alternative workplace strategy.
Incident reporting and policy violations
A remote employee has no colleague beside them to consult; so they delay reporting. The policy lists, with concrete examples, the situations to report while working remotely: loss or theft of the device, the device being used by someone else, clicking a suspicious link, loss of a printed document, something unusual on the home network. The reporting channel and out-of-hours phone number are in the policy. How the incident is assessed after reporting is explained in the incident management procedure guide.
To speed up reporting, write this principle clearly: an employee who reports a loss or mistake in time is assessed not because of the report but, if applicable, because of a deliberate violation. A frightened employee stays silent. The sanction for a violation is stated with reference to the disciplinary process under Annex A 6.4; withdrawal of remote working authorization is also one of the possible consequences.
Final check before going live:
- Does the scope leave supplier remote access to a separate procedure?
- In the personal device scenario, are the accessible information and the scope of corporate wipe clear?
- Are the physical security and printed document clauses observable behaviors?
- Have technical details been delegated to the standard, and are the references correct?
- Where are the employee declaration and the authorization record kept?
To prepare the remote working policy as a set consistent with your other IT policies and work instructions, see the corporate IT policies, procedures and work instructions page. The official source for the control is the ISO/IEC 27001 standard.
Frequently asked questions
Should the remote working policy be a separate document?
It isn’t mandatory. It can be written as a separate topic-specific policy or be a section of the acceptable use policy. It’s enough that rules specific to remote working, such as authorization, device scenarios and physical security, are clearly included.
Should remote working on personal devices be allowed?
It depends on the organization’s risk assessment. If it will be allowed, the scope of access is narrowed, corporate data is protected at application level, local data storage is limited, and the policy clearly states that the organization won’t access the personal area.
How should the use of printed documents at home be regulated?
Printing confidential information at home can be prohibited. Other documents are kept in a locked place and not thrown in household waste; they’re brought back to the office and handed into the disposal process, or destroyed by a method the organization approves.
Should the VPN type or encryption settings be written into the policy?
No. The policy states as a principle that the approved remote access method is used; the technology and settings go in the technical standard. When the technology changes, the policy doesn’t need re-approval.