What this policy is
Requires personnel to lock screens when stepping away and to clear sensitive materials from desks at end of day or when leaving a workstation unattended.
Why every organization needs one
Tailgating, shoulder-surfing, and casual photography of unattended screens are the easiest attacks to execute and the easiest to prevent.
What a competent Clear Desk And Clear Screen Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Screen-lock timeout requirement
- Sensitive-material handling at end of day
- Visitor escort obligations
- Printer and shared-workspace handling
- Review cadence (typically annual) and version control
- Approval, sign-off and effective date
How iCompaas tracks this policy
The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_clear_desk_and_clear_screen_policy_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).
Compliance frameworks that reference this policy
The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.
| Framework | Control | Title | Component |
|---|---|---|---|
| ISO/IEC 27001:2022 | A.7.7 | Clear desk and clear screen | Physical controls |
| ISO/IEC 27701:2025 | A.3.19 | Clear desk & screen | Security considerations |
2 controls across 2 frameworks reference this policy.
About this page
This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.