UnixTime

Research Note

ISO27001-A.7.7 Clear Desk and Clear Screen

People should not leave sensitive papers, removable media, printed documents, fax messages, or unlocked screens exposed where unauthorized people can see, photograph, remove, alter, or discard them.

On this page

Control Purpose

People should not leave sensitive papers, removable media, printed documents, fax messages, or unlocked screens exposed where unauthorized people can see, photograph, remove, alter, or discard them.

Use A.7.7 Clear Desk and Clear Screen for the detailed requirement, implementation guidance, audit checks, evidence expectations, and related ISO 27005 context.

Risk Logic

01 Asset What must be protected: data, service, process, person, or facility.
02 Threat Event, actor, or condition that can cause harm.
03 Vulnerability Weakness that makes the threat relevant.
04 Risk Scenario with likelihood, impact, owner, and priority.
05 Treatment Avoid, mitigate, transfer, or accept the risk.
06 Control Safeguard selected through ISO 27001/27002 and the SoA.
07 Evidence Record proving the control exists and operates.
08 Audit Independent verification, finding, or assurance result.

No published risk scenario is linked to this control yet. Create or link a risk note under the risk knowledge base before treating this control as fully mapped.

Detailed Note

Evidence Required

See A.7.7 Audit Evidence Pack.

Map this control to unattended information, shoulder surfing, photography, removable media loss, printer/fax exposure, misfiling, and disposal risk.

Audit Questions

  • AQ-ISO27001-A.7.7 Audit Question
  • How does the organization prove ISO27001-A.7.7 is implemented and operating?
  • What evidence shows ownership, review cadence, exceptions, and corrective action?
  • Which failed condition would create an audit finding for this control?
  • Iso27001
  • ISO27002
  • Annex a
  • Control
  • Clear desk clear screen

Note Metadata

Aliases: ISO27001-A.7.7

Source: 06-Control-Knowledge-Base/ISO27001-A.7.7-Clear-Desk-and-Clear-Screen.md

Control dependency map

How this control connects to work products

Generated from the static research graph. It shows navigation and evidence dependencies; it is not an audit conclusion.

3

links

01

Requirement context

Primary control text, framework notes, or adjacent controls this note points to.

02

Evidence required

Evidence packs and proof records that support auditability.

03

Audit checks

Audit questions, checklists, or review material connected to the control.

Graph-sourced resources

Templates and evidence

Auditor evidence packs

Evidence collections and audit-facing verification material.