ISO 27001:2022 Annex A 7.7 – Clear Desk and Clear Screen Explained

Most information leaks don’t involve hacking.
They involve what was left behind.

Annex A 7.7 exists to ensure organisations protect sensitive information on desks, screens, and shared workspaces, reducing the risk of unauthorised access, observation, loss, or misuse.

This control targets one of the simplest — and most overlooked — causes of data exposure.

ISO 27001

Quick Guide: Annex A 7.7 at a Glance

Annex A 7.7 of ISO 27001:2022 focuses on clear desk and clear screen practices.

At a practical level, this means:

  • Preventing sensitive information being left visible or accessible
  • Securing physical and digital materials when not in use
  • Reducing exposure in shared, public, or unattended environments
  • Reinforcing good day-to-day information handling behaviour

The control does not mandate a single policy format. It expects organisations to define and apply clear rules that reduce casual and opportunistic exposure.

In-Depth Guide to Annex A 7.7

What Is Annex A 7.7 and Why Does It Matter?

Unattended workspaces create easy opportunities for:

  • Unauthorised viewing of sensitive information
  • Accidental disclosure during meetings or presentations
  • Theft or misuse of documents or devices
  • Breaches caused by convenience rather than intent

Common examples include:

  • Unlocked screens in shared offices
  • Printed documents left on desks or printers
  • Whiteboards displaying sensitive information
  • Notifications or pop-ups visible to others

Annex A 7.7 addresses these everyday risks by promoting disciplined, repeatable handling of information, regardless of role or location.

This control replaces ISO 27001:2013 Annex A 11.2.9 and reflects modern working practices, including mobile devices and open-plan environments.

How to Implement Annex A 7.7 Effectively

A pragmatic approach to Annex A 7.7 typically includes the following elements.

1. Define Clear Desk and Clear Screen Expectations

Organisations should define what “clear” means in practice, including:

  • What information should not be left unattended
  • When desks and screens must be cleared
  • Which environments require stricter behaviour

Clarity prevents inconsistent interpretation.

2. Secure Physical Information When Not in Use

Physical materials containing sensitive information should be protected, for example by:

  • Storing documents in locked drawers or cabinets
  • Securing removable media when not in use
  • Avoiding leaving information on desks overnight

Paper remains a common source of exposure.

3. Protect Screens and Devices When Unattended

Screens should not display sensitive information when unattended.

Organisations typically apply:

  • Screen locking when stepping away
  • Automatic time-out and lock features
  • Authentication required to re-access devices

Unattended screens are one of the easiest access points for misuse.

4. Control Printing and Output Devices

Printers and shared devices introduce additional risk.

Organisations should consider:

  • Secure or authenticated printing
  • Prompt collection of printouts
  • Avoiding unattended output trays

Printed material is often forgotten — and easily seen.

5. Manage Display of Information in Shared Spaces

Sensitive information can be exposed unintentionally.

Annex A 7.7 supports defining rules for:

  • Screen notifications and pop-ups
  • Information displayed during presentations
  • Use and clearing of whiteboards

Visibility risk increases in meetings and public or shared environments.

6. Dispose of Sensitive Information Securely

When information is no longer required, it should be disposed of securely.

This may include:

  • Shredding paper documents
  • Secure disposal of media
  • Following defined disposal procedures

Clear desks are ineffective without secure disposal.

7. Address Vacated Workspaces and Facilities

When desks, rooms, or facilities are vacated, organisations should ensure:

  • Sensitive information is removed
  • Devices and media are secured or wiped
  • No residual information is left behind

End-of-use scenarios are frequently overlooked.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

Practical Considerations

Annex A 7.7 does not require:

  • Sterile or empty desks at all times
  • Constant enforcement or monitoring
  • Zero tolerance for minor lapses

It does require organisations to:

  • Reduce unnecessary exposure
  • Apply consistent, understood rules
  • Reinforce behaviour through awareness and example

This control works best when normalised, not policed.

Common Challenges and How to Overcome Them

  • Treating clear desk rules as cosmetic
  • Link behaviour to real exposure and risk
  • Ignoring screens and digital exposure
  • Apply clear screen rules alongside desk controls
  • Inconsistent behaviour across teams
  • Define expectations clearly and apply them broadly
  • Relying on reminders instead of habit
  • Reinforce through training, leadership example, and environment

Most breaches here are accidental — prevention is behavioural.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

Final Recommendations

Annex A 7.7 is about eliminating easy wins for unauthorised access.

When clear desk and clear screen practices are applied effectively:

  • Casual exposure is reduced
  • Insider and visitor risk decreases
  • Confidentiality is easier to maintain
  • Day-to-day security discipline improves

Sophisticated attacks get attention.
Annex A 7.7 prevents the simple ones that succeed far too often.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

The Annex Control Table

ISO 27001:2022 Organisational Controls
ISO 27001:2022 Technological Controls