The acceptable use policy is perhaps the only text among information security documents that every employee reads and accepts. Its reader isn’t an IT specialist; it’s an accountant, a sales representative, a production planner. That’s why it can’t be written like the other policies. Below we explain the scope of an acceptable use policy that meets the ISO/IEC 27001:2022 Annex A 5.10 control, how to write readable clauses, topic-based sample clauses and the points to watch from a KVKK perspective when monitoring employees.
Purpose and scope of the policy
Annex A 5.10 requires rules and procedures for the acceptable use and handling of information and other associated assets to be identified, documented and implemented. The policy is the employee-facing side of these rules. Its scope is shaped by its relationship with other controls: 5.11 covers return of assets on leaving, 6.4 the disciplinary process, 8.1 user endpoint devices. The acceptable use policy refers to these; it doesn’t replace them.
The scope section must answer three questions clearly:
- Who? Employees, interns, temporary staff and supplier personnel using the organization’s assets. For suppliers, the policy should be added to the contract or separately accepted.
- Which assets? Computers, phones, email, corporate cloud services and network access provided by the organization, printed documents, and personal devices on which organization data is processed.
- In which settings? Office, field, remote working. Rules specific to remote working can be kept in a separate policy; for that, see the article remote working security policy.
The relationship with the top-level policy follows the hierarchy described in the information security policy writing guide: the top-level policy sets the principle, the acceptable use policy defines employee behavior.
Writing readable clauses
Most employees read the policy once, on the acceptance screen. A clause not understood in that single reading isn’t applied. A picture you may come across is the “I have read and accept” box being ticked without the text being opened; if the text is long and written in legalese, this is unavoidable. These rules help readability:
- Write in the second person. Instead of “Users must not …”, write “Don’t use your work email for personal subscriptions.”
- Give the right way along with the prohibition. “Don’t upload company files to a personal cloud account; use the corporate sharing service for sharing externally.” A ban with no alternative produces shadow IT.
- Reduce technical terms. If you use the word “phishing”, explain what it is in one sentence.
- Split the rules into topics. Headings such as email, internet, cloud, devices and AI make it easier for employees to find the rule they’re looking for.
- Don’t use vague measures. Instead of “reasonable personal use”, describe with examples what’s accepted.
- Limit the length. Technical details stay in IT standards; the employee-facing text shouldn’t exceed a few pages.
Topic-based sample clauses
The table below shows a typical permission and a typical prohibition for each topic. Adapt the clauses to the tools the organization actually uses. The policy shouldn’t recommend an alternative the organization doesn’t provide; writing “use the corporate sharing service” without setting that service up pushes employees straight to personal accounts.
| Topic | Do | Don’t |
|---|---|---|
| Report suspicious emails with the report button or through the IT support channel. | Don’t use your work email for non-work memberships and subscriptions; don’t auto-forward work email to a personal address. | |
| Internet | If sites you need for work are blocked, request access from IT. | Don’t try to bypass blocking and filtering controls. |
| Cloud storage | Keep company files in the storage and sharing service provided by the organization. | Don’t move company data to personal cloud accounts, personal email or messaging apps. |
| Software | Request the software you need through the IT request process. | Don’t install unapproved software, browser extensions or remote access tools. |
| Personal devices | Access company data only from registered, managed devices. | Don’t download company data to a personal device’s local storage. |
| Accounts and passwords | If you suspect your account has been compromised, report it immediately. | Don’t share your password or verification code with anyone, including IT staff. |
| Printed documents | Don’t leave confidential documents on your desk; keep them in a locked cabinet. | Don’t throw confidential documents in the normal bin; use the secure disposal box. |
Regulate personal use explicitly. Organizations usually allow limited personal use; if it’s allowed, write down its limits (not affecting work performance, no illegal content or content that puts the organization at risk, no statements on behalf of the organization) and that this use may also fall within the scope of monitoring.
Use of generative AI tools
AI chat and writing tools are the newest and fastest-changing heading in acceptable use policies. Annex A has no control specific to these tools; the rules are derived from information classification (5.12), information transfer (5.14), supplier relationships and cloud services (5.19, 5.23) and protection of personal data (5.34). In practice the risk is simple. When a log file is pasted into a chat window, the internal IP addresses, user names and sometimes session keys in it go too. The policy should contain these decisions:
- Approved tool list: Tools the organization has assessed and contracted are separated from individual free accounts. Company data is used only in approved tools.
- Rules by data class: Which class of information can be entered into which tool is given as a table. For example, “public” information can be used in any tool, “internal” information only in the tool under corporate contract, and “confidential” information in none.
- Personal data: Entering personal data into a service hosted abroad may require a cross-border transfer assessment under Article 9 of KVKK. Personal data isn’t entered until this assessment has been made.
- Responsibility for output: Tool output isn’t passed to a customer, a public authority or a production system without being checked; responsibility for accuracy lies with the employee using it.
- Code and configuration: Source code, configuration files, logs and network information aren’t pasted into unapproved tools; this content may contain passwords, keys and internal addresses.
Monitoring and informing employees
This policy is where the organization explains to employees which records it monitors and for what purpose. Sign-in, email gateway, web filter and endpoint security logs on corporate systems contain personal data about employees. Logs are personal data. That’s why the monitoring section is written together with the legal unit, with these KVKK points in mind:
- Information notice: Under the information obligation in Article 10 of KVKK, employees are told which data is processed, for what purpose, on what legal basis and to whom it may be transferred. The acceptable use policy should refer to the employee privacy notice and must not contradict it.
- Legal basis: The legal unit determines which processing condition in Article 5 of KVKK the monitoring relies on. In an employment relationship, whether explicit consent rests on free will may be debatable; don’t set up a signed acceptance form as explicit consent until this has been assessed.
- Proportionality: Under the principles in Article 4 of KVKK, monitoring must be relevant, limited and proportionate to its purpose. If logs collected for security will be used for another purpose such as performance evaluation, this is assessed separately.
- Access and retention: Who can access monitoring records, in which situations, and how long they’re kept is defined; a separate approval step is put in place for intrusive operations such as content review.
To design these topics together with technical and organizational measures, you can draw on our KVKK technical and organizational measures work. Current Board decisions and guides should be followed on the official KVKK website.
Acceptance, signature and breach management
Evidence that the policy was read and accepted is one of the first records asked for in an audit. The acceptance process can be designed like this:
- A new employee reads and accepts the policy before access to company systems is granted; the acceptance is recorded in the HR file or the training platform. If access is opened first, acceptance is often never obtained.
- For significant revisions, existing employees accept again; minor changes are communicated by announcement.
- The policy’s core clauses are repeated in the annual awareness training; an attendance record is kept. How these records are presented in an audit is explained in the article training and awareness evidence.
- For supplier personnel, acceptance is obtained through a contract annex or an undertaking signed before access.
The breach section should be short and predictable: it states that when a breach is detected, the incident is recorded under the information security incident process, access may be temporarily suspended if needed, and the disciplinary process is run under the HR procedure within the scope of Annex A 6.4. Defining the types of sanctions in the disciplinary regulations rather than the policy keeps things consistent from an employment law perspective. Also add wording that encourages reporting of unintentional breaches. Early reporting limits the impact. An employee who immediately reports an email sent to the wrong recipient buys time for a recall or access revocation; an employee who thinks they’ll be punished stays silent.
Pre-publication checklist
- Next to each prohibition, the alternative the organization provides is stated.
- The limits of personal use are clearly written.
- AI rules are matched to the information classification scheme, and the approved tool list is published as a separate annex.
- The monitoring section is consistent with the employee privacy notice and has been approved by the legal unit.
- Where the acceptance record is kept, and the triggers for re-acceptance, are defined.
- The access rules don’t contradict the access control policy.
Preparing employee-facing policy texts together with the organization’s IT processes is part of our corporate IT policies and procedures work.
Frequently asked questions
Is an acceptable use policy mandatory in ISO 27001?
Annex A 5.10 requires rules for the acceptable use of information and associated assets to be identified, documented and implemented. If the control is applicable in the SoA, these rules must be written down; a separate policy is the most common method.
Is the employee’s signed acceptance enough for monitoring under KVKK?
It shouldn’t be considered enough on its own. The information obligation must be fulfilled separately, and the legal unit should determine which processing condition the monitoring is based on. Acceptance of the policy is evidence that the rules were read.
Is banning AI tools completely the right approach?
A complete ban pushes employees to use unapproved tools with personal accounts. A more workable way is to set approved tools and clearly define which data class can be used in which tool.
When should the policy be re-approved?
Get re-approval for significant revisions that change the rules or employee obligations. Corrections that don’t change the meaning can be communicated by announcement; the core clauses are repeated in the annual awareness training.