8.3 Information access restriction
The organization is to limit who can reach information and associated assets, following its established access control policy. Purpose: permit authorized access and block unauthorized access to information and associated assets. Guidance: to support restriction, consider not allowing unknown or anonymous identities to reach sensitive information, granting public or anonymous access only to locations holding nothing sensitive; configuration settings that govern who reaches what inside systems, applications and services; control over which data each user can reach; control over which identities or groups hold which permissions, for example reading, writing, deleting or executing; and physical or logical isolation of sensitive applications, their data or systems. Consider dynamic access management for high-value sensitive information where the organization needs fine-grained control over who accesses it, when and how; wants to share it externally while keeping control; wants to manage its use and distribution in real time; wants to prevent unapproved alteration, copying, forwarding or printing; wants to monitor its use; or wants a record of changes for possible investigation. Such techniques should protect information throughout creation, processing, storage, transmission and disposal, with rules per use case that grant permissions by identity, device, location or application and use the classification scheme to decide what needs this protection, backed by operating, monitoring and reporting processes and technical infrastructure. Dynamic access systems protect information by requiring authentication, credentials or a certificate; limiting access to a time window; encrypting it; setting print permissions; recording who uses it and how; and alerting on attempted misuse. Other information: these techniques can protect documents, emails and files even after they leave the organization, where ordinary controls cannot reach, adapting over the life cycle; they supplement rather than replace classic controls such as access control lists by adding conditions, real-time evaluation and just-in-time data reduction; permissions can be changed or withdrawn at any time, which aids incident response; ISO/IEC 29146 provides a framework.
Source: ISO/IEC 27002:2022, 8.3. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27002:2022 in the compliance library.
ISO/IEC 27002 is guidance on the Annex A controls; certification is against ISO/IEC 27001. Use this set when your sheet follows the 27002 numbering.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Rules and configuration for dynamic access management or rights management on high-value information (identity, device, location, time limits, printing, encryption) · Endpoint management (MDM / EDR)
- Usage logs and misuse alerts from dynamic access or rights management tooling · SIEM / log platform
periodic reviewEvidence produced at each review
- Evidence that anonymous or public access is limited to locations holding no sensitive information, for example storage bucket access reviews · Document repository
governing documentDocuments that govern the control
- System, application and cloud storage configurations restricting access by identity or group, with granular permissions per action · Policy repository / GRC workspace
- Isolation of sensitive applications, data or systems through physical or logical segmentation · Policy repository / GRC workspace
- Mapping of classification levels to the access restriction techniques applied · Policy repository / GRC workspace
First move
Common gaps auditors find
- Cloud storage or file shares allow anonymous access to sensitive data
- Permissions are granted to broad groups such as all staff
- Sensitive documents shared externally cannot be revoked or tracked
- Delete and execute permissions are granted where only read is needed
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet